-
-
Notifications
You must be signed in to change notification settings - Fork 849
Update Wins overlay to use different SVG #8378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Wins overlay to use different SVG #8378
Conversation
|
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes. |
|
Availability: after 1pm (pacific) |
daras-cu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @myronchen-git, great job on this issue, your code changes look good and the Wins page worked correctly when I tested it. The GitHub svg is displaying as it should at the correct size and you added the required aria-label attribute for accessibility.
One small fix before we merge-it looks like you may have an auto-formatter enabled that changed some of the white space in _wins-page.scss and wins.js. Can you please revert the lines that aren't part of your code changes? That way reviewers will have an easier time seeing the relevant changes, and the edit history on those files will be more clear.
Thanks for your work on this issue.
3277e48 to
b2756b9
Compare
b2756b9 to
cc1c87f
Compare
|
I have now removed the whitespace changes. Although, I do believe the files' whitespaces should be fixed. |
daras-cu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @myronchen-git, all looks good now. I do agree, I think there are white space issues throughout the codebase, we may do an audit at some point after we work through some of the more pressing issues.
kdaca19xx
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, myronchen-git!
Things Done Well
-
The pull request was done with the correct branch.
-
There's a linked issue. I read/understood it.
-
Your edits in the Files Changed tab looks good.
Suggestions
none.
Fixes #7937
What changes did you make?
updateOverlayfunction inwins.jsto attachhrefandaria-labelattributes to and hide/show the GitHub icons, as well as have the code for the LinkedIn icon utilize the new anchor element in the HTML.Why did you make the changes (we will use this info to test)?
_includes\svg\, the JavaScript code inassets/js/wins.jscould not access the_includesfolder. The workaround is to use theincludetag from Jekyll in the HTML.aria-labelneeded to be added to the GitHub icon to make it WCAG compliant.CodeQL Alerts
After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.
Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown
Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.
Instructions for resolving CodeQL alerts
If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.
In general, CodeQL alerts should be resolved prior to PR reviews and merging
Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)